XML Planning Group - Legislative Document Solutions

Legislative Solutions™ Demonstrations

Let us show you how its done
(reach us by email)

A comprehensive document solution should be multi-platform, language agnostic, and provide a robust environment that includes at least the following minimum features:

Document Editing:
The system should be characterized by the users’ ability to create, revise, and view documents that instantiate various classes. For example, a legislative user may need to create a new session law statement, amend a bill draft, or access and copy a fragment of a published statute. Each of these examples represents an instance of different, although often related, classes of documents. Determining these relationships and how to best implement them in an integrated system is a valuable skill that XML Planning can offer your organization.

Document Management:
Most modern organizations require an Internet-scalable, intelligent content repository for capturing, managing and processing all forms of structured data. In order to meet the evolving needs of a document-intensive organization, such a repository requires security/permission verification, document check-out/check-in, and revision history capture, at a minimum.

Composition:
Does the unique nature of your document suite require a system to compute and place page and line numbers into XML document streams in adherence with strict specifications dictated by law? Are the specific layouts, presentation and styles assigned to component parts of your documents mission-critical? The composition engine in a unified document solution should readily convert or transform the XML comprising your source documents into various output formats, e.g., PostScript, PCL, PDF, HTML, XHTML, etc. The automatic repurposing of your content for print, Web, and scfreen presentation will enhance the value of your data.

Workflow:
Workflow is characterized by the defined series of tasks that are required to produce a final outcome. At each stage of the document authoring process, do you find that one individual or group is responsible for a specific, defined, and measurable task? What happens when that task is satisfactorily completed? Integrated workflow software should ensure that the individual or group responsible for the next sequential (or otherwise related) task is notified and receives the data needed to efficiently and effectively execute subsequent stages of the process.

Content searching:
The ability to interactively or programmatically search a set of documents for XML elements, XML attributes, by text patterns, specifric content, context-sensitive data relations, and other combinations and mappings, is consider a key requirement of sophisticated document functionality. By building data-centric solutions, XML Planning can show you how to maximize your search capabilities.

Document specific operations:
Does your organization include certain document types that might require unique processing, composition, and construction operations to build the structure that characterizes their class. For example, some legislative bodies during the authoring of legal amendments create special reports that includes side-by-side comparisons of bills, before and after staff or committees have modified them. The value of these automated tools can be easily measured in demonstrable savings of time and money.

Archive/retrieval:
The means of long-term digital storage of XML encoded documents, fragments, and report components is an essential component of any data-centric document automation system. Even in cases where archived documents may not be retrieved for years, when necessary, simple and efficient indexing and searching is required.